I wrote this program to learn how to implement AppleEvents.
I wrote minimal AppleEvent receiving handlers (Required AppleEvents) and several AppleEvent sending procedures.
I hope this sample may help novice programmers who have felt AppleEvent is complicated.
This package includes three project files:
TC.sample.prj:
THINK C 8.0 (THINK Project Manager 7.0.4) project
CW.sample.68K.prj:
CodeWarrior IDE project for 68K
CW.sample.PPC.prj:
CodeWarrior IDE for PPC
I wrote the sources using CodeWarrior. I also confirmed they can be compiled with THINK C.
However, easier version than the 8.4 of Symantec C/C++ contains old-fashioned Universal Headers. If you use such versions, you will meet a lot of compile errors. Please use the Symantec C/C++ version 8.4 or greater.
The application: ﾒAESampleﾓ simply receives dragged and dropped files via AppleEvents and send some of AppleEvents to Finder or some application to open the files.
Its functions are not useful at all but I think it a good sample to learn how to work with AppleEvents.
It also has a function to send AppleEvents to designated Application using PPCBrowser. I hope it to be useful when debugging your AppleEvent receiving handlers.
2. To AppleEvent novices
ﾒsample.AE.cﾓ includes the minimal AppleEvent receiving handlers.
ﾒsample.send.cﾓ includes AppleEvent sending samples.
If you just want to implement Drag and Drop receiver from Finder, you can just quote ﾒsample.AE.cﾓ into your application.
If you want to send your AppleEvent, refer to ﾒsample.send.c.ﾓ
Be sure to check the Size Flag of your project when you make your own project file. The flag is absolutely needed when the application sends or receives AppleEvents.
If you use THINK C, you can set it using ﾒSet Project Type...ﾓ menu. If you use CodeWarrior, you can set it using ﾒProjectﾓ item of ﾒPreferences...ﾓ menu.
3. New features added in the version 0.1
3.1. Macintosh Drag and Drop
The version 0.1 newly includes file receiving procedures from Finder using Drag Manager (Macintosh Drag and Drop). Drag Manager itself is independent from AppleEvent implementation but I added it as an example of the High Level Event.
Here I describe some of peculiarities of Drag Manager. Drag Manager handlers allow global variable freely although they are callback. On the other hand, they offer strict limitation that they never allow process switching. This is a big problem for programmers because we cannot use source level debuggers. However we want to trace some trouble, Drag Manager never passes the process to the debugger and we will meet a lockup. So, we have to write source code very carefully.
In addition, Drag Manager handlers restrict inter-application communications. Since they never pass the process to the target applications, we cannot use any AppleEvents that expect reply events.
AESample 0.1 does not process the received files directly in the Drag Manager handler but sends the files to AESample itself using OpenDocument AppleEvents. By processing the files outside the Drag Manager handler, AESample 0.1 avoids potential inter-application problems.
AESample receives files by dragging and dropping files onto the ﾒOpenﾓ menu button. Note that the hiliting procedure of AESample does not follow the standard Drag Manager procedures.
3.2. Notification Manager
Implementing Macintosh Drag and Drop, I also had to change alert methods. Macintosh Drag and Drop allows to approach background applications and transact data. In case an application is in background, some error has occurred and shows an alert immediately, the alert would not be a front-most window and the user may not recognize what has gone wrong. Otherwise, you might think to force the application to be foreground but it would violate the human interface guideline. Therefore I implemented the Notification Manager according to the guideline.
3.3. EmbossDraw Library
AESample 0.1 includes several routines named EmbossDraw Library. They provide 3D-like lines and rectangle drawing procedures. AESample 0.1 uses them for drawing such as menu buttons of the main window.
Recent applications equip colorful user interface elements that are not provided by the standard MacOS API. I am interested in such elements and wrote several drawing routines. These are totally dependent items from AppleEvent implementation but I decided to include them expecting they would help you. Though I do not write any details of their usage, I think you will easily understand how to use them by reading the EmbossDraw.h
4. Terms of distribution and usage
Keep whole files including this document when you distribute this package.
Except it, I donﾕt lay any claims to this package. You can distribute it freely without the permission. You can change the archiving or compacting method as you like.
You can also use every code of the sources. You donﾕt need to ask for my permission nor authorization. You can use it not only for non-commercial but also commercial purposes.
5. Disclaimer
I am not responsible to any problems caused with the source codes of this package.
You should use it at your own risk.
6. Other notices
6.1. Scope
Scopes of functions and variables are set just for conveniences of AESample. You can modify them when you fit them in your sources.
6.2. BNDL setting
Sometimes, a few people wonder their programs don't accept Finder drag and drop though they implemented AppleEvent Handlers.
In that case, please check the followings:
whether if the 'BNDL' has been set needed file types.
Otherwise, whether if the 'BNDL' contains wild-card type: '****'.
If you have done so and it doesn't work yet, please try to rebuild the desktop.
7. Special thanks
The following persons helped me with their suggestions and source codes when I wrote this package: ﾒAE Sample.ﾓ I would like to express my thanking to them.
